Efficient bwp operation for sidelink operation

ABSTRACT

Apparatuses, methods, and systems are disclosed for selectively deactivating a bandwidth part. One apparatus 600 includes a transceiver 625 that receives 805 one or more UL BWP configurations and receives 810 a SL BWP configuration. Here, the one or more UL BWP configurations includes an active UL BWP and the SL BWP is associated with a first numerology. The apparatus 600 also includes a processor 605 that identifies 815 a second numerology of an active UL BWP and determines 820 whether the first numerology matches the second numerology. If the first numerology does not match the second numerology, the processor 605 selectively deactivates 825 one of the SL BWP and the active UL BWP.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/804,692 entitled “EFFICIENT BWP OPERATION FOR SIDELINK OPERATION”and filed on Feb. 12, 2019 for Joachim Loehr, Prateek Basu Mallick, andKarthikeyan Ganesan, which application is incorporated herein byreference.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to selectively deactivatinga bandwidth part in the case of a numerology mismatch between an uplinkbandwidth part and a sidelink bandwidth part.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), Fifth Generation Core Network (“5CG”),Fifth Generation System (“5GS”), Absolute Radio Frequency Channel Number(“ARFCN”), Authentication, Authorization and Accounting (“AAA”), Accessand Mobility Management Function (“AMF”), Access to Restricted LocalOperator Services (“ARLOS”), Positive-Acknowledgment (“ACK”),Application Programming Interface (“API”), Authentication Center(“AuC”), Access Stratum (“AS”), Autonomous Uplink (“AUL”), AUL DownlinkFeedback Information (“AUL-DFP”), Base Station (“BS”), Binary PhaseShift Keying (“BPSK”), Bandwidth Part (“BWP”), Cipher Key (“CK”), ClearChannel Assessment (“CCA”), Control Element (“CE”), Cyclic Prefix(“CP”), Cyclical Redundancy Check (“CRC”), Channel State Information(“CSI”), Common Search Space (“CSS”), Connection Mode (“CM”, this is aNAS state in 5GS), Core Network (“CN”), Control Plane (“CP”), Data RadioBearer (“DRB”), Discrete Fourier Transform Spread (“DFTS”), DownlinkControl Information (“DCI”), Downlink (“DL”), Downlink Pilot Time Slot(“DwPTS”), Dual Connectivity (“DC”), Dual Registration mode (“DR mode”),Discontinuous Transmission (“DTX”), Enhanced Clear Channel Assessment(“eCCA”), Enhanced Licensed Assisted Access (“eLAA”), Enhanced MobileBroadband (“eMBB”), Evolved Node-B (“eNB”), Evolved Packet Core (“EPC”),Evolved Packet System (“EPS”), EPS Mobility Management (“EMM”, this is aNAS state in EPS), Evolved UMTS Terrestrial Radio Access (“E-UTRA”),E-UTRA Absolute Radio Frequency Channel Number (“EARFCN”), Evolved UMTSTerrestrial Radio Access Network (“E-UTRAN”), EuropeanTelecommunications Standards Institute (“ETSI”), Frame Based Equipment(“FBE”), Frequency Division Duplex (“FDD”), Frequency Division MultipleAccess (“FDMA”), Frequency Division Orthogonal Cover Code (“FD-OCC”),General Packet Radio Service (“GPRS”), Generic Public Service Identifier(“GPSI”), Guard Period (“GP”), Global System for Mobile Communications(“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), HybridAutomatic Repeat Request (“HARQ”), Home Subscriber Server (“HSS”), HomePublic Land Mobile Network (“HPLMN”), Information Element (“IE”),Integrity Key (“IK”), Internet-of-Things (“IoT”), International MobileSubscriber Identity (“IMSI”), Key Derivation Function (“KDF”), LicensedAssisted Access (“LAA”), Load Based Equipment (“LBE”),Listen-Before-Talk (“LBT”), Long Term Evolution (“LTE”), Multiple Access(“MA”), Mobility Management (“MM”), Mobility Management Entity (“MME”),Modulation Coding Scheme (“MC S”), Machine Type Communication (“MTC”),Multiple Input Multiple Output (“MIMO”), Mobile Station InternationalSubscriber Directory Number (“MSISDN”), Multi User Shared Access(“MUSA”), Narrowband (“NB”), Negative-Acknowledgment (“NACK”) or(“NAK”), New Generation (5G) Node-B (“gNB”), New Generation Radio AccessNetwork (“NG-RAN”, a RAN used for 5GS networks), New Radio (“NR”, a 5Gradio access technology; also referred to as “5G NR”), Next Hop (“NH”),Next Hop Chaining Counter (“NCC”), Non-Access Stratum (“NAS”), NetworkExposure Function (“NEF”), Non-Orthogonal Multiple Access (“NOMA”),Network Slice Selection Assistance Information (“NS SAT”), Operation andMaintenance System (“OAM”), Orthogonal Frequency Division Multiplexing(“OFDM”), Packet Data Unit (“PDU”, used in connection with ‘PDUSession’), Packet Switched (“PS”, e.g., Packet Switched domain or PacketSwitched service), Primary Cell (“PCell”), Physical Broadcast Channel(“PBCH”), Physical Cell Identity (“PCP”), Physical Downlink ControlChannel (“PDCCH”), Physical Downlink Shared Channel (“PDSCH”), PatternDivision Multiple Access (“PDMA”), Physical Hybrid ARQ Indicator Channel(“PHICH”), Physical Random Access Channel (“PRACH”), Physical ResourceBlock (“PRB”), Physical Uplink Control Channel (“PUCCH”), PhysicalUplink Shared Channel (“PUSCH”), Public Land Mobile Network (“PLMN”),Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”),Radio Access Network (“RAN”), Radio Access Technology (“RAT”), RadioResource Control (“RRC”), Random-Access Channel (“RACH”), Random AccessResponse (“RAR”), Radio Network Temporary Identifier (“RNTI”), ReferenceSignal (“RS”), Registration Area (“RA”, similar to tracking area listused in LTE/EPC), Registration Management (“RM”, refers to NAS layerprocedures and states), Remaining Minimum System Information (“RMSI”),Resource Spread Multiple Access (“RSMA”), Round Trip Time (“RTT”),Receive (“RX”), Radio Link Control (“RLC”), Sparse Code Multiple Access(“SCMA”), Scheduling Request (“SR”), Single Carrier Frequency DivisionMultiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Shared Channel(“SCH”), Session Management (“SM”), Session Management Function (“SMF”),Service Provider (“SP”), Sidelink (“SL”), Sidelink Control Information(“SCP”), Signal-to-Interference-Plus-Noise Ratio (“SINR”), SingleNetwork Slice Selection Assistance Information (“S-NSSAI”), SingleRegistration mode (“SR mode”), Sounding Reference Signal (“SRS”), SystemInformation Block (“SIB”), Synchronization Signal (“SS”), SubcarrierSpacing (“SCS”), Supplementary Uplink (“SUL”), Subscriber IdentificationModule (“SIM”), Tracking Area (“TA”), Transport Block (“TB”), TransportBlock Size (“TB S”), Time-Division Duplex (“TDD”), Time DivisionMultiplex (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”),Transmission Time Interval (“TTI”), Transmit (“TX”), Unified AccessControl (“UAC”), Unified Data Management (“UDM”), User Data Repository(“UDR”), Uplink Control Information (“UCI”), User Entity/Equipment(Mobile Terminal) (“UE”), UE Configuration Update (“UCU”), UE RouteSelection Policy (“URSP”), Uplink (“UL”), User Plane (“UP”), UniversalMobile Telecommunications System (“UMTS”), UMTS SubscriberIdentification Module (“USIM”), UMTS Terrestrial Radio Access (“UTRA”),UMTS Terrestrial Radio Access Network (“UTRAN”), Uplink Pilot Time Slot(“UpPTS”), Ultra-reliability and Low-latency Communications (“URLLC”),Visited Public Land Mobile Network (“VPLMN”), and WorldwideInteroperability for Microwave Access (“WiMAX”). As used herein,“HARQ-ACK” may represent collectively the Positive Acknowledge (“ACK”)and the Negative Acknowledge (“NACK”) and Discontinuous Transmission(“DTX”). ACK means that a TB is correctly received while NACK (or NAK)means a TB is erroneously received. DTX means that no TB was detected.

In certain wireless communication systems, sidelink transmission allowsone UE device to communicate directly with another UE, e.g., viadevice-to-device (“D2D”) communications. Bandwidth part operation adaptsthe size of the bandwidth used for data transmission (e.g., on awideband carrier). In Rel-15 3GPP networks, a serving cell may beconfigured with up to four uplink bandwidth parts.

BRIEF SUMMARY

Disclosed are procedures for selectively deactivating a bandwidth part.One method of a UE for selectively deactivating a bandwidth partincludes receiving one or more UL bandwidth part (“BWP”) configurationsfor a serving cell, including an active UL BWP and receiving a SL BWPconfiguration for the same serving cell, wherein the SL BWP isassociated with a first numerology. The method includes identifying asecond numerology of the active UL BWP and determining whether the firstnumerology matches the second numerology. The method includesselectively deactivating one of the SL BWP and the active UL BWP if thefirst numerology does not match the second numerology.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for selectively deactivating a bandwidthpart;

FIG. 2 is a diagram illustrating one embodiment of a networkarchitecture for selectively deactivating a bandwidth part;

FIG. 3 is a flowchart diagram illustrating one embodiment prioritizingUL over SL;

FIG. 4 is a diagram illustrating one embodiment of prioritizing SL overUL;

FIG. 5 is a diagram illustrating one embodiment ofactivation/deactivation information;

FIG. 6 is a diagram illustrating one embodiment of a user equipmentapparatus that may be used for selectively deactivating a bandwidthpart;

FIG. 7 is a diagram illustrating one embodiment of a base stationapparatus that may be used for selectively deactivating a bandwidthpart; and

FIG. 8 is a flowchart diagram illustrating one embodiment of a methodthat may be used for selectively deactivating a bandwidth part.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects.

For example, the disclosed embodiments may be implemented as a hardwarecircuit comprising custom very-large-scale integration (“VLSI”) circuitsor gate arrays, off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. The disclosed embodiments mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices, or the like. As another example, the disclosed embodiments mayinclude one or more physical or logical blocks of executable code whichmay, for instance, be organized as an object, procedure, or function.

Furthermore, embodiments may take the form of a program product embodiedin one or more computer readable storage devices storing machinereadable code, computer readable code, and/or program code, referredhereafter as code. The storage devices may be tangible, non-transitory,and/or non-transmission. The storage devices may not embody signals. Ina certain embodiment, the storage devices only employ signals foraccessing code.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random-access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object-oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

As used herein, a list with a conjunction of “and/or” includes anysingle item in the list or a combination of items in the list. Forexample, a list of A, B and/or C includes only A, only B, only C, acombination of A and B, a combination of B and C, a combination of A andC or a combination of A, B and C. As used herein, a list using theterminology “one or more of” includes any single item in the list or acombination of items in the list. For example, one or more of A, B and Cincludes only A, only B, only C, a combination of A and B, a combinationof B and C, a combination of A and C or a combination of A, B and C. Asused herein, a list using the terminology “one of” includes one and onlyone of any single item in the list. For example, “one of A, B and C”includes only A, only B or only C and excludes combinations of A, B andC. As used herein, “a member selected from the group consisting of A, B,and C,” includes one and only one of A, B, or C, and excludescombinations of A, B, and C.” As used herein, “a member selected fromthe group consisting of A, B, and C and combinations thereof” includesonly A, only B, only C, a combination of A and B, a combination of B andC, a combination of A and C or a combination of A, B and C.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. This code may be provided to a processor of ageneral-purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart diagramsand/or block diagrams.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the flowchartdiagrams and/or block diagrams.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart diagrams and/or block diagrams.

The flowchart diagrams and/or block diagrams in the Figures illustratethe architecture, functionality, and operation of possibleimplementations of apparatuses, systems, methods, and program productsaccording to various embodiments. In this regard, each block in theflowchart diagrams and/or block diagrams may represent a module,segment, or portion of code, which includes one or more executableinstructions of the code for implementing the specified logicalfunction(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

Generally, the present disclosure describes systems, methods, andapparatus for bandwidth part operation for remote units 105 engaged insidelink (e.g., vehicular) communication. In various embodiments,sidelink (“SL”) communication uses the PC5 interface. Sidelinkcommunications may allocate (unused) UL resources to communicatedevice-to-device with another UE.

To enable Bandwidth adaption, i.e., adapting the size of the bandwidthused for data transmission in a serving cell the gNB configures the UEwith UL and DL Bandwidth Part(s) (BWP). In paired spectrum, DL and ULcan switch BWP independently. In unpaired spectrum, DL and UL switch BWPsimultaneously. Switching between configured BWPs happens by means of aDCI, i.e. PDCCH indicating to switch to another Bandwidth part, orinactivity timer. When an inactivity timer is configured for a servingcell, the expiry of the inactivity timer associated to that cell mayswitch from the active BWP to a default BWP configured by the network.

In certain embodiments, a Serving Cell may be configured with up to fourBWPs, and for an activated Serving Cell, there is always one active BWPat any point in time. While the present disclosure assumes a maximum offour BWPs per Serving Cell, the principles described herein apply toother wireless communication systems supporting more BWPs per servingcell.

The BWP switching for a Serving Cell is used to activate an inactive BWPand deactivate an active BWP at a time and is controlled by the PDCCHindicating a downlink assignment or an uplink grant. Upon addition ofSpCell or activation of an SCell, one BWP is initially active withoutreceiving PDCCH indicating a downlink assignment or an uplink grant.

On the active BWP for each activated Serving Cell configured with a BWP,the MAC entity is to apply normal operations. This includes transmittingon UL-SCH, transmitting on RACH, monitoring the PDCCH, transmittingPUCCH, receiving DL-SCH, and (re-)initializing any suspended configureduplink grants of configured grant Type 1 according to the storedconfiguration.

On the inactive BWP for each activated Serving Cell configured with aBWP, the MAC entity is not to transmit on UL-SCH, is not to transmit onRACH, is not to monitor the PDCCH, is not to transmit PUCCH, is not toreceive DL-SCH, is to clear any configured downlink assignment andconfigured uplink grant of configured grant Type 2, and is to suspendany configured uplink grant of configured Type 1.

If the active UL BWP has no PRACH resources configured, the UE shallupon triggering of a RACH procedure switch to the initial DL BWP and ULBWP and perform RACH procedure. If the MAC entity receives a PDCCH forBWP switching while a Random Access procedure is ongoing in the MACentity, it is up to UE implementation whether to switch BWP or ignorethe PDCCH for BWP switching. If the MAC entity decides to perform BWPswitching, the MAC entity shall stop the ongoing Random Access procedureand initiate a Random Access procedure on the new activated BWP. If theMAC decides to ignore the PDCCH for BWP switching, the MAC entity shallcontinue with the ongoing Random Access procedure on the active BWP.

As mentioned before, the 3GPP Rel-15 NR specifications allow only oneactive BWP at a time. In Rel-15 each BWP has an associated numerology,i.e., each BWP supports only one numerology. For cases in Rel-15 when UEsupports services requiring different numerologies, gNB needs to switchbetween different configured BWP(s). However, wireless networks mayexpect the UE to use the same numerology in the configured SL BWP andthe active BWP in the same carrier at a given time.

Where only one SL BWP configured for a carrier/serving cell, it is notpossible to switch to another SL BWP, e.g., to align with the numerologyof current active UL BWP. Therefore, the SL BWP may be considered to bealways active. Given the fact that there is only one SL BWP, the SL BWPis to be considered immediately active as soon as it is configured.

However, if at the time the SL BWP is configured the UL BWP in use atthat point of time (when RRC Reconfiguration is received) has adifferent SCS/Numerology than the configured SL BWP, then management ofthe UL BWP is needed.

Disclosed herein are procedures and related signaling for efficientmanagement of the configured UL and/or SL BWP in a carrier/serving cell,in particular for cases of a numerology mismatch between the active ULBWP and the configured SL BWP.

FIG. 1 depicts a wireless communication system 100 for selectivelydeactivating a bandwidth part, according to embodiments of thedisclosure. In one embodiment, the wireless communication system 100includes at least one remote unit 105, a radio access network (“RAN”)120, and a mobile core network 140. The RAN 120 and the mobile corenetwork 140 form a mobile communication network. The RAN 120 may becomposed of a base unit 110 with which the remote unit 105 communicatesusing wireless communication links 115. Even though a specific number ofremote units 105, base units 110, wireless communication links 115, RANs120, and mobile core networks 140 are depicted in FIG. 1, one of skillin the art will recognize that any number of remote units 105, baseunits 110, wireless communication links 115, RANs 120, and mobile corenetworks 140 may be included in the wireless communication system 100.

In one implementation, the wireless communication system 100 iscompliant with the 5G system specified in the 3GPP specifications. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication network, for example, LTEor WiMAX, among other networks. The present disclosure is not intendedto be limited to the implementation of any particular wirelesscommunication system architecture or protocol.

In one embodiment, the remote units 105 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), smart appliances (e.g.,appliances connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 105 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 105 may be referred toas the UEs, subscriber units, mobiles, mobile stations, users,terminals, mobile terminals, fixed terminals, subscriber stations, userterminals, wireless transmit/receive unit (“WTRU”), a device, or byother terminology used in the art.

The remote units 105 may communicate directly with one or more of thebase units 110 in the RAN 120 via uplink (“UL”) and downlink (“DL”)communication signals. Furthermore, the UL and DL communication signalsmay be carried over the wireless communication links 115. Here, the RAN120 is an intermediate network that provides the remote units 105 withaccess to the mobile core network 140.

In some embodiments, the remote units 105 communicate with anapplication server 151 via a network connection with the mobile corenetwork 140. For example, an application 107 (e.g., web browser, mediaclient, telephone/VoIP application) in a remote unit 105 may trigger theremote unit 105 to establish a PDU session (or other data connection)with the mobile core network 140 via the RAN 120. The mobile corenetwork 140 then relays traffic between the remote unit 105 and theapplication server 151 in the packet data network 150 using the PDUsession. Note that the remote unit 105 may establish one or more PDUsessions (or other data connections) with the mobile core network 140.As such, the remote unit 105 may concurrently have at least one PDUsession for communicating with the packet data network 150 and at leastone PDU session for communicating with another data network (not shown).

The base units 110 may be distributed over a geographic region. Incertain embodiments, a base unit 110 may also be referred to as anaccess terminal, an access point, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, or by any other terminologyused in the art. The base units 110 are generally part of a radio accessnetwork (“RAN”), such as the RAN 120, that may include one or morecontrollers communicably coupled to one or more corresponding base units110. These and other elements of radio access network are notillustrated but are well known generally by those having ordinary skillin the art. The base units 110 connect to the mobile core network 140via the RAN 120.

The base units 110 may serve a number of remote units 105 within aserving area, for example, a cell or a cell sector, via a wirelesscommunication link 115. The base units 110 may communicate directly withone or more of the remote units 105 via communication signals.Generally, the base units 110 transmit DL communication signals to servethe remote units 105 in the time, frequency, and/or spatial domain.Furthermore, the DL communication signals may be carried over thewireless communication links 115. The wireless communication links 115may be any suitable carrier in licensed or unlicensed radio spectrum.The wireless communication links 115 facilitate communication betweenone or more of the remote units 105 and/or one or more of the base units110.

In one embodiment, the mobile core network 140 is a 5G core (“5GC”) orthe evolved packet core (“EPC”), which may be coupled to a packet datanetwork 150, like the Internet and private data networks, among otherdata networks. A remote unit 105 may have a subscription or otheraccount with the mobile core network 140. Each mobile core network 140belongs to a single public land mobile network (“PLMN”). The presentdisclosure is not intended to be limited to the implementation of anyparticular wireless communication system architecture or protocol.

The mobile core network 140 includes several network functions (“NFs”).As depicted, the mobile core network 140 includes multiple user planefunctions (“UPFs”) 145. The mobile core network 140 also includesmultiple control plane functions including, but not limited to, anAccess and Mobility Management Function (“AMF”) 141 that serves the RAN120, a Session Management Function (“SMF”) 143, and a Policy ControlFunction (“PCF”) 147. In certain embodiments, the mobile core network140 may also include an Authentication Server Function (“AUSF”), aUnified Data Management function (“UDM”) 149, a Network RepositoryFunction (“NRF”) (used by the various NFs to discover and communicatewith each other over APIs), or other NFs defined for the 5GC.

In various embodiments, the mobile core network 140 supports differenttypes of mobile data connections and different types of network slices,wherein each mobile data connection utilizes a specific network slice.Here, a “network slice” refers to a portion of the mobile core network140 optimized for a certain traffic type or communication service. Incertain embodiments, the various network slices may include separateinstances of network functions, such as the SMF 143 and UPF 145. In someembodiments, the different network slices may share some common networkfunctions, such as the AMF 141. The different network slices are notshown in FIG. 1 for ease of illustration, but their support is assumed.

Although specific numbers and types of network functions are depicted inFIG. 1, one of skill in the art will recognize that any number and typeof network functions may be included in the mobile core network 140.Moreover, where the mobile core network 140 is an EPC, the depictednetwork functions may be replaced with appropriate EPC entities, such asan MME, S-GW, P-GW, HSS, and the like. In certain embodiments, themobile core network 140 may include a AAA server.

In various embodiments, the remote units 105 may communicate directlywith each other (e.g., device-to-device communication) using sidelink(“SL”) communication signals 125. Here, sidelink transmissions from a“transmitting” remote unit 105 may be broadcast, groupcast or unicast.Groupcast refers to group communications where the transmitting remoteunit 105 in the group transits a multicast packet to all its groupmembers.

While FIG. 1 depicts components of a 5G RAN and a 5G core network, thedescribed embodiments for selectively deactivating a bandwidth partapply to other types of communication networks, including IEEE 802.11variants, GSM, GPRS, UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee,Sigfoxx, and the like. For example, in an LTE variant involving an EPC,the AMF 141 may be mapped to an MME, the SMF 143 may be mapped to acontrol plane portion of a PGW and/or to an MME, the UPF 145 may bemapped to an SGW and a user plane portion of the PGW, the UDM/UDR 149may be mapped to an HSS, etc.

To support BWP operation for SL communication, in particular where thereis a mismatch between the active UL BWP's and the configured SL BWP'snumerology, the remote unit 105 may be configured with a communicationpriority policy, e.g., a set of one or more communication priorityrules.

In some embodiments, UL communication is prioritized over SLcommunication. Here, the SL BWP may be implicitly deactivated by the UEwhen the active UL BWP has a different numerology than the SL BWP. Asused herein, “deactivated” means that no SL transmission and receptionis supported for the serving cell/carrier when the (single) configuredSL BWP is deactivated, e.g. no SL communication on the configured SLResource Pools (“RPs”). Further, the phrase “implicitly deactivated”means that the remote unit 105 is to deactivate the SL BWP on the basisof the differing numerologies and without explicit signaling from thebase unit 110 to the remote unit 105 to deactivate the SL BWP.

Moreover, in the UL-first priority scheme, the SL BWP may be implicitlyactivated by the UE when the active UL BWP has the same numerology thanthe SL BWP. As used herein, “activated” means SL transmission andreception is (again) available on the serving cell/carrier, e.g. theconfigured SL (Resource Pools) RPs are again usable for SLcommunication. Further, the phrase “implicitly activated” means that theremote unit 105 is to activate (e.g., reactivate) the SL BWP on thebasis of the same numerologies and without explicit signaling from thebase unit 110 to the remote unit 105 to activate the SL BWP. Note thatan instruction to switch to a UL BWP with the same numerology as theconfigured SL BWP implicitly instructs the remote unit 105 to activatethe SL BWP (which may have been deactivated previously).

In some embodiments, SL communication is prioritized over ULcommunication. Here, if the current UL BWP has a numerology that isdifferent than the SL BWP, then the remote unit 105 may autonomouslyswitch (e.g., without explicit instruction from the base unit 110) fromthe current UL BWP to a configured UL BWP which has the same numerologyas the SL BWP. Where the remote unit 105 is configured with multiple ULBWPs having the same numerology as the SL BWP, then the remote unit 105may refer to a rule governing which of the multiple UL BWPs the remoteunit 105 is to switch to. In one example, the rule may instruct theremote unit 105 to switch to a UL BWP (of the multiple matching BWP)having a smallest BWP identifier.

Moreover, in the SL-first priority scheme, if there is no configured ULBWP with the same numerology as the SL BWP, then the remote unit 105 maydeactivate the SL BWP.

In other embodiments, activation/deactivation of a configured SL BWP isto be explicitly signaled by the base unit 110. Here, the SL BWP may beactivated/deactivated by a separate message from the DCI used to switch(activate/deactivate) the (UL) BWP. In certain embodiments, a controlmessage is used to signal SL BWP activation/deactivation. In oneembodiment, the control message is a compact DCI. In another embodiment,the control message is a MAC CE. In certain embodiments, SL BWPactivation/deactivation is signaled by means of a SL resource allocationmessage. In certain embodiments, the SL BWP is activated a fixed (e.g.,default) time after receiving an RRC reconfiguration message (e.g., toconfigure the same numerology as the UL BWP).

FIG. 2 depicts a network architecture 200 for selectively deactivating abandwidth part, according to embodiments of the disclosure. The networkarchitecture 200 includes a first UE 205 in communication with a gNB 210and a second UE 215. Here, the first UE 205 is configured with a UL BWP220, a DL BWP 225, and a SL BWP 230.

In the depicted embodiment, the UE 205 supports simultaneous UL BWP 220and SL BWP 230 having the same numerology but does not supportsimultaneous UL BWP 220 and SL BWP 230 having different numerology.Accordingly, the UE 205 selectively deactivates a configured BWP (e.g.,the SL BWP and/or a UL BWP) if a numerology mismatch is detected.

According to a first solution, the UE 205 deactivates the configured SLBWP 230 when the numerology of the active UL BWP 220 in a givencarrier/serving cell differs from the numerology of the SL BWP 230configured for the same carrier/serving cell. Deactivation of the SL BWP230 is done autonomously in the UE 205. This solution is described ingreater detail below with reference to FIG. 3.

According to a second solution, the UE 205 autonomously switches to aconfigured UL BWP 220 which has the same numerology as the SL BWP 230 incase the current active UL BWP's numerology is different compared to thenumerology of the SL BWP 230. This solution is described in greaterdetail below with reference to FIG. 4.

According to a third solution, a network entity such as the gNB 210,explicitly activates/deactivates a configured SL BWP 230 by means ofcontrol signaling.

According to a fourth solution, the UE 205 is allowed to communicate onan active UL BWP 220 with a numerology different to the SL BWP'snumerology in slots which are reserved for NR UL and which are at leasta predefined time, e.g. x ms, ahead of the next slot configured for SLcommunication, i.e. there should be a gap of at least x ms between theNR UL operation and NR SL communication.

According to a fifth solution, the UE 205 upon receiving a RRC(Re)configuration message configuring a SL BWP 230 with a numerology notmatching the active UL BWP's numerology, i.e., SL BWP's numerology isdifferent than the active UL BWP's numerology, considers theconfiguration as invalid, i.e., the UE 205 is unable to comply with theconfiguration. As a consequence, the UE 205 ignores the RRC(re)configuration message, i.e. the UE 205 continues using theconfiguration used prior to the reception of RRCReconfiguration message.

According to a sixth solution, the UE 205 may ignore a PDCCH (DCI)ordering the UE 205 to switch to an UL BWP 220 associated with anumerology being different than the configured SL BWP's numerology.Similarly, the UE 205 may ignore an RRC message ordering the UE 205 toswitch/activate an UL BWP 220 associated with a numerology beingdifferent than the configured SL BWP's numerology.

According to a seventh solution, the UE 205 is configured whether itshould act according to the behavior described in the first solution,e.g. prioritizing UL over SL by autonomously deactivating SL BWP 230 incase of numerology mismatch, or whether it should act according to thebehavior described in the second solution, e.g. prioritizing SL over ULby switching UL BWP 220 in case of numerology mismatch.

FIG. 3 depicts a procedure 300 for selectively deactivating a configuredBWP, according to embodiments of the disclosure. The procedure 300 maybe implemented by a UE, such as the UE 205. The procedure 300illustrates a first solution for BWP numerology mismatch. The UEdetermines whether the active UL BWP and the SL BWP have the samenumerology (see block 305). If the active UL BWP and the SL BWP have thesame numerology, then they both remain active (see block 310).Otherwise, according to the first solution, the UE 205 autonomouslydeactivates the SL BWP when a numerology mismatch is detected (see block315).

In certain embodiments, such numerology mismatch may happen in case thegNB 210 orders the UE 205—e.g. by means of a PDCCH indicating a downlinkassignment or an uplink grant or—to switch to one of the configured ULBWP 220 having a different numerology than the numerology associatedwith the configured SL BWP 230. Another situation where such numerologymismatch may occur is when UE autonomously switches to thedefault/initial BWP having a different numerology than the SL BWP 230.The UE 205 may switch to the default/initial BWP when e.g. no RACHresources are configured on the serving cell.

As discussed above, deactivating the SL BWP 230 is to be understood asdisabling SL communication on the corresponding carrier/serving cell,e.g., the UE 205 cannot transmit or receive SL communication on theconfigured resource pools. For the case where the UE 205 has multipleactive UL BWPs 220 for a carrier/serving cell, at least one of thenumerologies associated with the active UL BWPs 220 needs to match theSL BWP's numerology, otherwise the UE 205 will autonomously deactivatethe SL BWP 230, as described above.

Similar to the (implicit) deactivation of the SL BWP—when there is amismatch between the active UL BWP's and the configured SL BWP'snumerology—the UE 205 activates the configured SL BWP 230 when theactive UL BWP's numerology is the same as the configured SL BWP'snumerology. For example, when UE 205 switches to an UL BWP 220 with samenumerology as the SL BWP's numerology—e.g. by network order—the UE 205implicitly activates the SL BWP 230 (which was, for example, previouslydeactivated). Activating the SL BWP 230 is to be understood as enablingSL communication in the corresponding carrier/serving cell, e.g. the UE205 can transmit or receive SL communication on the configured resourcepools in the cell.

FIG. 4 depicts a procedure 400 for selectively deactivating a bandwidthpart, according to embodiments of the disclosure. The procedure 400 maybe implemented by a UE, such as the UE 205. The procedure 400illustrates a second solution for BWP numerology mismatch. The UEdetermines whether the active UL BWP and the SL BWP have the samenumerology (see block 405). If the active UL BWP and the SL BWP have thesame numerology, then they both remain active (see block 410).Otherwise, according to the second solution, the UE 205 autonomouslyswitches to a configured UL BWP which has the same numerology as the SLBWP upon detecting the numerology mismatch (see block 415).

In certain embodiments, such numerology mismatch (e.g., SCS mismatch)may happen in case the gNB 210 configured a SL BWP 230 for acarrier/serving cell having a different numerology than the currentactive UL BWP's numerology. For cases when there are multiple configuredUL BWPs 220 having the same numerology (e.g., SCS) as the SL BWP'snumerology, the UE 205 may switch to one of the multiple configured ULBWPs 220 with the same numerology according to at least one of thefollowing selections rules:

In one embodiment, the selected UL BWP is the one having the smallestBWP ID. In another embodiment, the selected UL BWP is the one having thehighest BWP ID.

In certain embodiments, the selected UL BWP is the one having thelargest overlap with the SL BWP, i.e. overlap of the UL BWP's PRB andthe SL BWP's PRBs.

In one embodiment, the selected UL BWP is the default UL BWP, providedthat the default UL BWP has the same numerology as the SL BWP. Inanother embodiment, the selected UL BWP is the initial UL BWP, providedthat the initial UL BWP has the same numerology as the SL BWP.

Accordingly, the UE 205 tries to maintain both UL and SL communicationsby switching to a compatible UL BWP (e.g., one with the same numerologyas the SL BWP). In one implementation of the second solution, the UE 205deactivates the SL BWP 230 for cases when there is no configured UL BWP220 having the same numerology as the SL BWP 230.

FIG. 5 depicts control signaling 500 for selectivelyactivating/deactivating a bandwidth part, according to embodiments ofthe disclosure. The control signaling 500 may be transmitted by a RANnode, such as the gNB 210, to a UE, such as the UE 205. The controlsignaling 500 may be used to explicitly activate and/or deactivate aconfigured SL BWP.

According to the third solution, a network entity such as the gNB 210,explicitly activates/deactivates a configured SL BWP 230 by means ofcontrol signaling. For example, when a configured SL BWP 230 iscurrently deactivated, e.g. due to a mismatching numerology as describedin the first embodiment, the gNB 210 may decide to quickly activate theSL BWP 230 in order to ensure that SL communication can be performed inthe serving cell.

According to one implementation of the third solution, activating a SLBWP 230 by means of some explicit signaling may cause the UE 205 todeactivate/switch the current active UL BWP 220, e.g., for cases whenthe numerologies are not matching as explained in above embodiments.

According to some implementations of the third solution, theactivation/deactivation information may be conveyed in an existing V2Xcontrol channel allocating resources for SL communication, e.g. as shownin FIG. 5.

A new field may be introduced in the existing V2X control channelindicating the activation/deactivation status of the SL BWP 230.Alternatively, a resource allocation on the SL BWP 230 may implicitlyactivate the SL BWP 230. Similarly, an invalid resource allocation mayimplicitly indicate to deactivate the SL BWP 230.

Alternatively, PHY signaling is used to activate/deactivate a SL BWP230. For example, a new PDCCH format (e.g., DCI) may be used whichindicates the UE 205 to activate (alternatively, deactivate) aconfigured SL BWP 230. The DCI may contain a flag indicating whether toactivate or deactivate a configured SL BWP 230 which may be identifiedby some BWP ID being also signaled within the SL-DCI.

According to another implementation of the third solution, a DCIindicating the activation of an UL BWP 220 having a different numerology(SCS) as the SL BWP's numerology implicitly deactivates the SL BWP 230.

According to a further implementation of the third solution, a MACcontrol element may be used to activate/deactivate a configured SL BWP230. In one alternative, a configured SL BWP 230 is activated uponhaving received an RRC reconfiguration message configuring a SL BWP 230having the same numerology as the active UL BWP's numerology, e.g., afix/default time duration after having received the RRC message.

According to a fourth solution, the UE 205 is allowed to communicate onan active UL BWP 220 with a numerology different to the SL BWP'snumerology in slots which are reserved for NR UL and which are at leasta predefined time, e.g. x ms, ahead of the next slot configured for SLcommunication, i.e. there should be a gap of at least x ms between theNR UL operation and NR SL communication. It should be noted that allslots/subframes offering PRBs intended for PC5 (SL) communicationsconstitute a SL Resource Pool. In order to allow sufficient time forswitching the numerology, the UE 205 stops UL transmissions on theactive UL BWP 220 a predefined time, e.g. x ms, before the next SL slot,i.e. slot/subframe belonging to the SL resource pool. Upon havingstopped UL transmissions, e.g. deactivated the UL BWP 220, the UE 205autonomously switches its numerology to the SL BWP's numerology in orderto be able to perform SL communication in the next SL slot/subframe.

The predefined time used for switching the numerology may be for examplederived based on RAN4 requirements with respect to BWP switching delay.Similarly, the UE 205 stops SL communication, e.g. deactivates the SLBWP 230, a predefined time before the next UL slot in order to switchthe numerology to the active UL BWP's numerology.

According to the fifth solution, the UE 205 upon receiving a RRC(Re)configuration message configuring a SL BWP 230 with a numerology notmatching the active UL BWP's numerology, i.e. SL BWP's numerology isdifferent than the active UL BWP's numerology, considers theconfiguration as invalid, i.e. the UE 205 is unable to comply with theconfiguration. As a consequence, the UE 205 ignores the RRC(re)configuration message, i.e. the UE 205 continues using theconfiguration used prior to the reception of RRCReconfiguration message.

The UE 205 may according to one implementation of the fifth solutionfurther trigger the connection re-establishment procedure. The behaviorupon reception of a RRC reconfiguration message configuring a SL BWP 230with a numerology different to the active UL BWP's numerology isaccording to another implementation of the fifth solution similar to theprocedure “Inability to comply with RRCReconfiguration” specified inTS38.331.

Specifically, if the UE 205 is operating in EN-DC, then if the UE isunable to comply with (part of) the configuration included in theRRCReconfiguration message received over SRB3, the UE 205 is to continueusing the configuration used prior to the reception ofRRCReconfiguration message and is to initiate the SCG failureinformation procedure to report SCG reconfiguration error, upon whichthe connection reconfiguration procedure ends. Otherwise, if the UE 205operating in EN-DC is unable to comply with (part of) the configurationincluded in the RRCReconfiguration message received over SRB1, the UE isto continue using the configuration used prior to the reception ofRRCReconfiguration message and is to initiate the connectionre-establishment procedure, upon which the connection reconfigurationprocedure ends.

Otherwise, if the RRCReconfiguration is received via NR, then if the UEis unable to comply with (part of) the configuration included in theRRCReconfiguration message, the UE is to continue using theconfiguration used prior to the reception of RRCReconfiguration messageand—if security has not been activated—the UE is to perform the actionsupon going to RRC_IDLE, with release cause ‘other’. However, if ASsecurity has been activated but SRB2 and at least one DRB have not beensetup, then the UE is to perform the actions upon going to RRC_IDLE,with release cause ‘RRC connection failure’. Else, the UE is to initiatethe connection re-establishment procedure, upon which thereconfiguration procedure ends.

According to another implementation of the fifth solution, the UE 205goes to RRC_IDLE state upon reception of an RRC reconfiguration messageconfiguring a SL BWP 230 with an associated numerology different thanthe active UL BWP's numerology.

According to a sixth solution, the UE 205 may ignore a PDCCH (DCI)ordering the UE 205 to switch to an UL BWP 220 associated with anumerology being different than the configured SL BWP's numerology.Similarly, the UE 205 may ignore an RRC message ordering the UE 205 toswitch/activate an UL BWP 220 associated with a numerology beingdifferent than the configured SL BWP's numerology. According to oneimplementation of the sixth solution, the UE 205 doesn't switch to thedefault respectively initial UL BWP 220 in case the numerologyassociated with the default/initial UL BWP 220 is different to the SLBWP's numerology.

According to a seventh solution, the UE 205 is configured whether itshould act according to the behavior described in the first solution,e.g. prioritizing UL over SL by autonomously deactivating SL BWP 230 incase of numerology mismatch, or whether it should act according to thebehavior described in the second solution, e.g. prioritizing SL over ULby switching UL BWP 220 in case of numerology mismatch.

In one alternative implementation of the seventh solution, the UE 205acts according to the behavior described in either the first or secondsolution depending on the priority of the logical channels configuredfor NR UL and SL. Where the NR traffic has a higher priority than the SLtraffic, the UE 205 behaves prioritizes UL over SL in case of anumerology mismatch, as described above. Where the SL traffic has ahigher priority than NR UL traffic (e.g. logical channel priority of SLLCHs/RBs are higher than logical channel priority of the NR LCHs/RBs),the UE 205 prioritizes SL over UL in case of a numerology mismatch, asdescribed above.

Note that the priority of the different interfaces, e.g. NR-Uu and SLPC5, may be also defined by a V2X control function for a geographicalarea, i.e. in a certain geographical area (e.g. zone) NR-Uu (UL) isprioritized over SL leading in case of a numerology mismatch, whereas inother geographical areas SL PC5 operation is prioritized over Uumandating the UE 205 to act according to the second solution.

According to another implementation of the seventh solution, the UE 205switches in case of numerology mismatch to a UL BWP 220 having the samenumerology as the SL BWP 230 if such a UL BWP 220 is configured;otherwise the UE 205 deactivates the SL BWP 230.

FIG. 6 depicts a user equipment apparatus 600 that may be used forselectively deactivating a bandwidth part, according to embodiments ofthe disclosure. In various embodiments, the user equipment apparatus 600is used to implement one or more of the solutions described above. Theuser equipment apparatus 600 may be one embodiment of the UE 205,described above. Furthermore, the user equipment apparatus 600 mayinclude a processor 605, a memory 610, an input device 615, an outputdevice 620, and a transceiver 625. In some embodiments, the input device615 and the output device 620 are combined into a single device, such asa touchscreen. In certain embodiments, the user equipment apparatus 600may not include any input device 615 and/or output device 620. Invarious embodiments, the user equipment apparatus 600 may include one ormore of: the processor 605, the memory 610, and the transceiver 625, andmay not include the input device 615 and/or the output device 620.

The processor 605, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 605 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 605 executes instructions stored in thememory 610 to perform the methods and routines described herein. Theprocessor 605 is communicatively coupled to the memory 610, the inputdevice 615, the output device 620, and the transceiver 625.

In various embodiments, the transceiver 625 receives sidelink bandwidthpart (“BWP”) configuration and also receives one or more uplink BWPconfigurations. The processor 605 may identify a first subcarrierspacing of the sidelink BWP, identify a second subcarrier spacing of anactive uplink BWP, and determine whether the first subcarrier spacingmatches the second subcarrier spacing. If the subcarrier spacings do notmatch, then the processor 605 selectively deactivates one of thesidelink BWP and the active uplink BWP.

In some embodiments, the processor 605 determines a priority of thesidelink BWP with respect to the active uplink BWP, wherein selectivelydeactivating one of the sidelink BWP and the active uplink BWP is basedon the determined priority. In certain embodiments, the processor 605determines a priority of the sidelink BWP with respect to the activeuplink BWP, wherein selectively deactivating one of the sidelink BWP andthe active uplink BWP is based on the determined priority. If the activeuplink BWP has a higher priority than the sidelink BWP, then selectivelydeactivating one of the sidelink BWP and the active uplink BWP comprisesdeactivating the sidelink BWP.

In certain embodiments, the transceiver 625 receives an instruction toswitch to a second uplink BWP, the second uplink BWP having a subcarrierspacing that matches that of the sidelink BWP. Here, the processor 605reactivates the sidelink BWP in response to switching to the seconduplink BWP.

In certain embodiments, the sidelink BWP is a higher priority than theactive uplink BWP. In such embodiments, selectively deactivating one ofthe sidelink BWP and the active uplink BWP includes switching from theactive uplink BWP to a second uplink BWP, the second uplink BWP having asubcarrier spacing that matches that of the sidelink BWP. Where multipleconfigured uplink BWPs have a subcarrier spacing that matches that ofthe sidelink BWP, the processor 605 selects the second uplink BWP fromthe multiple matching uplink BWPs using a selection rule.

In certain embodiments, selectively deactivating one of the sidelink BWPand the active uplink BWP comprises deactivating the sidelink BWP inresponse to none of the one or more uplink BWP configurations having asubcarrier spacing that matches that of the sidelink BWP. In certainembodiments, the transceiver 625 receives a control message from anetwork entity, wherein the processor 605 deactivates a specified one ofthe sidelink BWP and the active uplink BWP according to the controlmessage.

The memory 610, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 610 includes volatile computerstorage media. For example, the memory 610 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 610 includes non-volatilecomputer storage media. For example, the memory 610 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 610 includes bothvolatile and non-volatile computer storage media.

In some embodiments, the memory 610 stores data related to selectivelydeactivating a bandwidth part. For example, the memory 610 may store ULBWP configurations, SL BWP configurations, BWP numerologies, and thelike. In certain embodiments, the memory 610 also stores program codeand related data, such as an operating system or other controlleralgorithms operating on the remote unit 105.

The input device 615, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 615 maybe integrated with the output device 620, for example, as a touchscreenor similar touch-sensitive display. In some embodiments, the inputdevice 615 includes a touchscreen such that text may be input using avirtual keyboard displayed on the touchscreen and/or by handwriting onthe touchscreen. In some embodiments, the input device 615 includes twoor more different devices, such as a keyboard and a touch panel.

The output device 620, in one embodiment, is designed to output visual,audible, and/or haptic signals. In some embodiments, the output device620 includes an electronically controllable display or display devicecapable of outputting visual data to a user. For example, the outputdevice 620 may include, but is not limited to, an LCD display, an LEDdisplay, an OLED display, a projector, or similar display device capableof outputting images, text, or the like to a user. As another,non-limiting, example, the output device 620 may include a wearabledisplay separate from, but communicatively coupled to, the rest of theuser equipment apparatus 600, such as a smart watch, smart glasses, aheads-up display, or the like. Further, the output device 620 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the output device 620 includes one or morespeakers for producing sound. For example, the output device 620 mayproduce an audible alert or notification (e.g., a beep or chime). Insome embodiments, the output device 620 includes one or more hapticdevices for producing vibrations, motion, or other haptic feedback. Insome embodiments, all or portions of the output device 620 may beintegrated with the input device 615. For example, the input device 615and output device 620 may form a touchscreen or similar touch-sensitivedisplay. In other embodiments, the output device 620 may be located nearthe input device 615.

As discussed above, the transceiver 625 communicates with one or morenetwork functions of a mobile communication network via one or moreaccess networks. The transceiver 625 operates under the control of theprocessor 605 to transmit messages, data, and other signals and also toreceive messages, data, and other signals. For example, the processor605 may selectively activate the transceiver 625 (or portions thereof)at particular times in order to send and receive messages.

The transceiver 625 may include one or more transmitters 630 and one ormore receivers 635. Although only one transmitter 630 and one receiver635 are illustrated, the user equipment apparatus 600 may have anysuitable number of transmitters 630 and receivers 635. Further, thetransmitter(s) 630 and the receiver(s) 635 may be any suitable type oftransmitters and receivers. Additionally, the transceiver 625 maysupport at least one network interface 640. Here, the at least onenetwork interface 640 facilitates communication with a RAN node, such asan eNB or gNB, for example using the “Uu” interface. Additionally, theat least one network interface 640 may include an interface used forcommunications with one or more network functions in the mobile corenetwork, such as a UPF, an AMF, and/or a SMF.

In one embodiment, the transceiver 625 includes a firsttransmitter/receiver pair used to communicate with a mobilecommunication network over licensed radio spectrum and a secondtransmitter/receiver pair used to communicate with a mobilecommunication network over unlicensed radio spectrum. In certainembodiments, the first transmitter/receiver pair used to communicatewith a mobile communication network over licensed radio spectrum and thesecond transmitter/receiver pair used to communicate with a mobilecommunication network over unlicensed radio spectrum may be combinedinto a single transceiver unit, for example a single chip performingfunctions for use with both licensed and unlicensed radio spectrum. Insome embodiments, the first transmitter/receiver pair and the secondtransmitter/receiver pair may share one or more hardware components. Forexample, certain transceivers 625, transmitters 630, and receivers 635may be implemented as physically separate components that access ashared hardware resource and/or software resource, such as for example,the network interface 640.

In various embodiments, one or more transmitters 630 and/or one or morereceivers 635 may be implemented and/or integrated into a singlehardware component, such as a multi-transceiver chip, asystem-on-a-chip, an application-specific integrated circuit (“ASIC”),or other type of hardware component. In certain embodiments, one or moretransmitters 630 and/or one or more receivers 635 may be implementedand/or integrated into a multi-chip module. In some embodiments, othercomponents such as the network interface 640 or other hardwarecomponents/circuits may be integrated with any number of transmitters630 and/or receivers 635 into a single chip. In such embodiment, thetransmitters 630 and receivers 635 may be logically configured as atransceiver 625 that uses one more common control signals or as modulartransmitters 630 and receivers 635 implemented in the same hardware chipor in a multi-chip module.

FIG. 7 depicts a base station apparatus 700 that may be used forselectively deactivating a bandwidth part, according to embodiments ofthe disclosure. The base station apparatus 700 may be one embodiment ofthe base unit 110, described above. Furthermore, the base stationapparatus 700 may include a processor 705, a memory 710, an input device715, an output device 720, and a transceiver 725. In some embodiments,the input device 715 and the output device 720 are combined into asingle device, such as a touchscreen. In certain embodiments, the basestation apparatus 700 may not include any input device 715 and/or outputdevice 720. In various embodiments, the base station apparatus 700 mayinclude one or more of: the processor 705, the memory 710, and thetransceiver 725, and may not include the input device 715 and/or theoutput device 720.

The processor 705, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 705 may be amicrocontroller, a microprocessor, a CPU, a GPU, an auxiliary processingunit, a FPGA, or similar programmable controller. In some embodiments,the processor 705 executes instructions stored in the memory 710 toperform the methods and routines described herein. The processor 705 iscommunicatively coupled to the memory 710, the input device 715, theoutput device 720, and the transceiver 725.

In various embodiments, the processor 705 controls the base stationapparatus 700 to perform the above describe behaviors. In someembodiments, the base station apparatus 700 sends to a UE (e.g., via thetransceiver 725) one or more UL BWP configurations and a SL BWPconfiguration. Here, the one or more UL BWP configurations includes anactive UL BWP. The SL BWP is associated with a first numerology and theactive UL BWP is associated with a second numerology. If the firstnumerology does not match the second numerology, the UE selectivelydeactivates one of the SL BWP and the active UL BWP, as described above.

The memory 710, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 710 includes volatile computerstorage media. For example, the memory 710 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 710 includes non-volatilecomputer storage media. For example, the memory 710 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 710 includes bothvolatile and non-volatile computer storage media.

In some embodiments, the memory 710 stores data related to selectivelydeactivating a bandwidth part. For example, the memory 710 may store ULBWP configurations, SL BWP configurations, BWP numerologies, and thelike. In certain embodiments, the memory 710 also stores program codeand related data, such as an operating system or other controlleralgorithms operating on the remote unit 105.

The input device 715, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 715 maybe integrated with the output device 720, for example, as a touchscreenor similar touch-sensitive display. In some embodiments, the inputdevice 715 includes a touchscreen such that text may be input using avirtual keyboard displayed on the touchscreen and/or by handwriting onthe touchscreen. In some embodiments, the input device 715 includes twoor more different devices, such as a keyboard and a touch panel.

The output device 720, in one embodiment, is designed to output visual,audible, and/or haptic signals. In some embodiments, the output device720 includes an electronically controllable display or display devicecapable of outputting visual data to a user. For example, the outputdevice 720 may include, but is not limited to, an LCD display, an LEDdisplay, an OLED display, a projector, or similar display device capableof outputting images, text, or the like to a user. As another,non-limiting, example, the output device 720 may include a wearabledisplay separate from, but communicatively coupled to, the rest of thebase station apparatus 700, such as a smart watch, smart glasses, aheads-up display, or the like. Further, the output device 720 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the output device 720 includes one or morespeakers for producing sound. For example, the output device 720 mayproduce an audible alert or notification (e.g., a beep or chime). Insome embodiments, the output device 720 includes one or more hapticdevices for producing vibrations, motion, or other haptic feedback. Insome embodiments, all or portions of the output device 720 may beintegrated with the input device 715. For example, the input device 715and output device 720 may form a touchscreen or similar touch-sensitivedisplay. In other embodiments, the output device 720 may be located nearthe input device 715.

The transceiver 725 includes at least transmitter 730 and at least onereceiver 735. One or more transmitters 730 may be used to communicatewith the UE, as described herein. Similarly, one or more receivers 735may be used to communicate with other network functions in the PLMN, asdescribed herein. Although only one transmitter 730 and one receiver 735are illustrated, the base station apparatus 700 may have any suitablenumber of transmitters 730 and receivers 735. Further, thetransmitter(s) 725 and the receiver(s) 730 may be any suitable type oftransmitters and receivers.

FIG. 8 depicts one embodiment of a method 800 for selectivelydeactivating a bandwidth part, according to embodiments of thedisclosure. In various embodiments, the method 800 is performed by theremote unit 105, the UE 205 and/or the user equipment apparatus 600,described above. In some embodiments, the method 800 is performed by aprocessor, such as a microcontroller, a microprocessor, a CPU, a GPU, anauxiliary processing unit, a FPGA, or the like.

The method 800 begins and receives 805 one or more UL BWP configurationsfor a serving cell, including an active UL BWP. The method 800 includesreceiving 810 a SL BWP configuration for the same serving cell, whereinthe SL BWP is associated with a first numerology. The method 800includes identifying 815 a second numerology of the active UL BWP.

The method 800 includes determining 820 whether the first numerologymatches the second numerology. The method 800 includes selectivelydeactivating 825 one of the SL BWP and the active UL BWP if the firstnumerology does not match the second numerology. The method 800 ends.

Disclosed herein is a first apparatus for selectively deactivating abandwidth part, according to embodiments of the disclosure. The firstapparatus may be implemented by a UE, such as the remote unit 105, theUE 205 and/or the user equipment apparatus 600. The first apparatusincludes a transceiver that receives one or more UL BWP configurationsand receives a SL BWP configuration. Here, the one or more UL BWPconfigurations includes an active UL BWP and the SL BWP is associatedwith a first numerology. The first apparatus also includes a processorthat identifies a second numerology of an active UL BWP and determineswhether the first numerology matches the second numerology. If the firstnumerology does not match the second numerology, the processorselectively deactivates one of the SL BWP and the active UL BWP.

In some embodiments, selectively deactivating one of the SL BWP and theactive UL BWP includes deactivating the SL BWP, wherein the processorfurther stops SL communication on that serving cell. In furtherembodiments, the transceiver may receive an instruction to switch to asecond UL BWP, the second UL BWP having a numerology that matches thatof the SL BWP. In such embodiments, the processor reactivates the SL BWPin response to switching to the second UL BWP.

In some embodiments, selectively deactivating one of the SL BWP and theactive UL BWP includes the processor switching from the active UL BWP toa second UL BWP that has a numerology that matches that of the SL BWP.In such embodiments, multiple configured UL BWPs may have a numerologythat matches that of the SL BWP. Accordingly, the processor selects thesecond UL BWP from the multiple matching UL BWPs using a selection rule.

In some embodiments, selectively deactivating one of the SL BWP and theactive UL BWP includes the processor deactivating the SL BWP in responseto none of the one or more UL BWP configurations having a numerologythat matches that of the SL BWP.

In some embodiments, the transceiver receives a control message from anetwork entity, the control message activating the SL BWP. In certainembodiments, selectively deactivating one of the SL BWP and the activeUL BWP includes the processor deactivating the active UL BWP in responseto activating the SL BWP according to the control message. In otherembodiments, selectively deactivating one of the SL BWP and the activeUL BWP includes the processor switching from the active UL BWP to asecond UL BWP that has a numerology that matches that of the SL BWP inresponse to activating the SL BWP according to the control message.

In some embodiments, the transceiver receives a control message from anetwork entity, the control message activating a configured UL BWPhaving a different numerology than the SL BWP. In such embodiments,selectively deactivating one of the SL BWP and the active UL BWPincludes the processor deactivating the SL BWP in response to activatingthe UL BWP according to the control message.

In some embodiments, selectively deactivating one of the SL BWP and theactive UL BWP includes the processor providing a communication gapbetween UL operation and SL operation and adjusting (e.g., retuningand/or reconfiguring) the transceiver to switch between the firstnumerology and the second numerology during the communication gap.

In some embodiments, the processor further determines a priority of theSL BWP with respect to the active UL BWP. In such embodiments,selectively deactivating one of the SL BWP and the active UL BWPincludes the processor deactivating a lower priority one of the SL BWPand the active UL BWP.

Disclosed herein is a first method for selectively deactivating abandwidth part, according to embodiments of the disclosure. The firstmethod may be performed by a UE, such as the remote unit 105, the UE 205and/or the user equipment apparatus 600. The first method includesreceiving one or more UL BWP configurations for a serving cell andreceiving a SL BWP configuration for the same serving cell. Here, theone or more UL BWP configurations for the serving cell includes anactive UL BWP and the SL BWP is associated with a first numerology. Thefirst method includes identifying a second numerology of the active ULBWP and determining whether the first numerology matches the secondnumerology. The first method includes selectively deactivating one ofthe SL BWP and the active UL BWP if the first numerology does not matchthe second numerology.

In some embodiments, selectively deactivating one of the SL BWP and theactive UL BWP includes deactivating the SL BWP. In such embodiments, thefirst method further includes stopping SL communication on that servingcell. In certain embodiments, the first method also includes receivingan instruction to switch to a second UL BWP having a numerology thatmatches that of the SL BWP and reactivating the SL BWP in response toswitching to the second UL BWP.

In some embodiments, selectively deactivating one of the SL BWP and theactive UL BWP includes switching from the active UL BWP to a second ULBWP that has a numerology that matches that of the SL BWP. In variousembodiments, multiple configured UL BWPs have a numerology that matchesthat of the SL BWP. In such embodiments, the first method includesselecting the second UL BWP from the multiple matching UL BWPs using aselection rule.

In some embodiments, selectively deactivating one of the SL BWP and theactive UL BWP includes deactivating the SL BWP in response to none ofthe one or more UL BWP configurations having a numerology that matchesthat of the SL BWP.

In some embodiments, the first method includes receiving a controlmessage from a network entity, the control message activating the SLBWP. In such embodiments, selectively deactivating one of the SL BWP andthe active UL BWP may include deactivating the active UL BWP in responseto activating the SL BWP according to the control message. In otherembodiments, selectively deactivating one of the SL BWP and the activeUL BWP may include switching from the active UL BWP to a second UL BWPthat has a numerology that matches that of the SL BWP in response toactivating the SL BWP according to the control message.

In some embodiments, the first method includes receiving a controlmessage from a network entity, the control message activating aconfigured UL BWP having a different numerology than the SL BWP. In suchembodiments, selectively deactivating one of the SL BWP and the activeUL BWP may include deactivating the SL BWP in response to activating theUL BWP according to the control message.

In some embodiments, selectively deactivating one of the SL BWP and theactive UL BWP includes providing a communication gap between ULoperation and SL operation and adjusting (e.g., retuning and/orreconfiguring) a transceiver to switch between the first numerology andsecond numerology during the communication gap.

In some embodiments, the first method includes determining a priority ofthe SL BWP with respect to the active UL BWP. In such embodiments,selectively deactivating one of the SL BWP and the active UL BWPincludes deactivating a lower priority one of the SL BWP and the activeUL BWP.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. A method of a UE comprising: receiving one or more uplink bandwidthpart (“BWP”) configurations for a serving cell, including an activeuplink BWP; receiving a sidelink BWP configuration for the same servingcell, wherein the sidelink BWP is associated with a first numerology;identifying a second numerology of the active uplink BWP; determiningwhether the first numerology matches the second numerology; andselectively deactivating one of the sidelink BWP and the active uplinkBWP in response to the first numerology not matching the secondnumerology.
 2. The method of claim 1, wherein selectively deactivatingone of the sidelink BWP and the active uplink BWP comprises deactivatingthe sidelink BWP, the method further comprising: stopping sidelinkcommunication on that serving cell.
 3. The method of claim 2, whereinthe method further comprises: receiving an instruction to switch to asecond uplink BWP, the second uplink BWP having a numerology thatmatches that of the sidelink BWP; and reactivating the sidelink BWP inresponse to switching to the second uplink BWP.
 4. The method of claim1, wherein selectively deactivating one of the sidelink BWP and theactive uplink BWP comprises switching from the active uplink BWP to asecond uplink BWP that has a numerology that matches that of thesidelink BWP.
 5. The method of claim 3, wherein multiple configureduplink BWPs have a numerology that matches that of the sidelink BWP, themethod further comprising selecting the second uplink BWP from themultiple matching uplink BWPs using a selection rule.
 6. The method ofclaim 1, wherein selectively deactivating one of the sidelink BWP andthe active uplink BWP comprises deactivating the sidelink BWP inresponse to none of the one or more uplink BWP configurations having anumerology that matches that of the sidelink BWP.
 7. The method of claim1, further comprising: receiving a control message from a networkentity, the control message activating the sidelink BWP, whereinselectively deactivating one of the sidelink BWP and the active uplinkBWP comprises deactivating the active uplink BWP in response toactivating the sidelink BWP according to the control message.
 8. Themethod of claim 1, further comprising: receiving a control message froma network entity, the control message activating the sidelink BWP,wherein selectively deactivating one of the sidelink BWP and the activeuplink BWP comprises switching from the active uplink BWP to a seconduplink BWP that has a numerology that matches that of the sidelink BWPin response to activating the sidelink BWP according to the controlmessage.
 9. The method of claim 1, further comprising: receiving acontrol message from a network entity, the control message activating aconfigured uplink BWP having a different numerology than the sidelinkBWP, and wherein selectively deactivating one of the sidelink BWP andthe active uplink BWP comprises deactivating the sidelink BWP inresponse to activating the uplink BWP according to the control message.10. The method of claim 1, wherein selectively deactivating one of thesidelink BWP and the active uplink BWP comprises: providing acommunication gap between uplink operation and sidelink operation; andadjusting a transceiver to switch between the first numerology andsecond numerology during the communication gap.
 11. The method of claim1, further comprising determining a priority of the sidelink BWP withrespect to the active uplink BWP, wherein selectively deactivating oneof the sidelink BWP and the active uplink BWP comprises deactivating alower priority one of the sidelink BWP and the active uplink BWP.
 12. Anapparatus comprising: a transceiver that: receives one or more uplinkbandwidth part (“BWP”) configurations, including an active uplink BWP;and receives a sidelink BWP configuration, wherein the sidelink BWP isassociated with a first numerology; and a processor that: identifies asecond numerology of an active uplink BWP; determines whether the firstnumerology matches the second numerology; and selectively deactivatesone of the sidelink BWP and the active uplink BWP in response to thefirst numerology not matching the second numerology.
 13. The apparatusof claim 12, wherein selectively deactivating one of the sidelink BWPand the active uplink BWP comprises deactivating the sidelink BWP,wherein the processor further stops sidelink communication on thatserving cell.
 14. The method of claim 13, wherein the transceiverfurther receives an instruction to switch to a second uplink BWP, thesecond uplink BWP having a numerology that matches that of the sidelinkBWP; and wherein the processor reactivates the sidelink BWP in responseto switching to the second uplink BWP.
 15. The apparatus of claim 12,wherein selectively deactivating one of the sidelink BWP and the activeuplink BWP comprises the processor switching from the active uplink BWPto a second uplink BWP that has a numerology that matches that of thesidelink BWP.
 16. The apparatus of claim 15, wherein multiple configureduplink BWPs have a numerology that matches that of the sidelink BWP,wherein the processor selects the second uplink BWP from the multiplematching uplink BWPs using a selection rule.
 17. The apparatus of claim12, wherein selectively deactivating one of the sidelink BWP and theactive uplink BWP comprises the processor deactivating the sidelink BWPin response to none of the one or more uplink BWP configurations havinga numerology that matches that of the sidelink BWP.
 18. The apparatus ofclaim 12, wherein the transceiver further receives a control messagefrom a network entity, the control message activating the sidelink BWP,wherein selectively deactivating one of the sidelink BWP and the activeuplink BWP comprises the processor deactivating the active uplink BWP inresponse to activating the sidelink BWP according to the controlmessage.
 19. The apparatus of claim 12, wherein the transceiver furtherreceives a control message from a network entity, the control messageactivating the sidelink BWP, wherein selectively deactivating one of thesidelink BWP and the active uplink BWP comprises the processor switchingfrom the active uplink BWP to a second uplink BWP that has a numerologythat matches that of the sidelink BWP in response to activating thesidelink BWP according to the control message.
 20. The apparatus ofclaim 12, wherein the transceiver further receives a control messagefrom a network entity, the control message activating a configureduplink BWP having a different numerology than the sidelink BWP, andwherein selectively deactivating one of the sidelink BWP and the activeuplink BWP comprises the processor deactivating the sidelink BWP inresponse to activating the uplink BWP according to the control message.